PATHSCAN v 1.41                                               January 3, 1995

In response to a number of requests PathScan now displays the version number for each
file if the file contains a version information.

A couple of text-formatting problems with low resolution video drivers were
also fixed.

-------------------------------------------------------------------------------------

PATHSCAN v 1.03                                               October 10, 1994

PathScan is a utility I wrote to simulate the Windows LoadLibrary and WinExec calls.
It's like a file find utility, except it searches across the Windows and DOS paths.

I write a lot of DLLs, and I used to constantly have a problem determining which of 
multiple copies of my target DLL were being loaded by windows during a debugging 
or testing session.  PathScan was built to tell me that.

When Windows loads a DLL or runs an EXE it searches for the target file in this order:

	1. already loaded in memory
	2. the current directory
	3. the Windows directory
	4. the Windows\System directory
	5. the DOS path

To use PathScan, you enter a file specification (e.g. TEST.DLL, TE??.DLL, TE*.D*) and
select a current directory.  PathScan will then simulate the Windows load procedure and
report all instances of the target specification it finds in the same order Windows
would find them during an actual load.

To test PathScan, select any current directory, enter USER.EXE as the file
specification, enter Windows Path and the Search Type and press the Search button.  If
your Windows setup is typical PathScan will find one copy of USER.EXE in memory and
one in the Windows\System directory.

PathScan is free, but use it at your own risk.  I would appreciate hearing from
you if you have any comments or suggestions.


Drew Stoddard
CompuServe: 71036,1320
Internet: dstod@ix.netcom.com